PK67545: INCORRECT CODE GENERATED BY ADD MEDIATION HANDLER WIZARD

Rational Application Developer for WebSphere Software, Version 7.0.0.8
6.1.1.8: WebSphere Application Server Toolkit Version 6.1.1 Fix Pack 8

APAR status

• Closed as program error.

Error description

• The problem appears to be with the code generated in the
  deployment descriptor by the Add Mediation Handler wizard.
  
  Instead of generating tags like this:
  <local-home>com.ibm.websphere.sib.mediation.handler.ejb.GenericE
  JBMediationHandlerLocalHome</local-home>
  <local>com.ibm.websphere.sib.mediation.handler.ejb.GenericEJBMed
  iationHandlerLocal</local>
  <ejb-class>com.ibm.websphere.sib.mediation.handler.ejb.GenericEJ
  BMediationHandlerBean</ejb-class>
  
  it generates tags like this:
  <local-home>com.MyMediationHandlerLocalHome</local-home>
  <local>com.MyMediationHandlerLocal</local>
  <ejb-class>com.ibm.websphere.sib.mediation.handler.ejb.GenericEJ
  BMediationHandlerBean</ejb-class>
  
  So the mediation handler class is never invoked at run time.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  Toolkit v6.1.1 and Rational Application     *
  *                  Developer v7.0 users                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Adding a new EJB mediation handler      *
  *                      causes incorrect local-home and local   *
  *                      interfaces to be defined in the         *
  *                      ejb-jar.xml file.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When adding a new EJB mediation handler the local-home
  interface and local interface for the enterprise bean are
  created based on the name of the mediation handler rather than
  the default
  com.ibm.websphere.sib.mediation.handler.ejb.GenericEJBMed
  iationHandler* interfaces.
  

Problem conclusion

• The logic for adding a new EJB mediation handler has been
  corrected so that any new EJB mediation handler will always
  create a local home interface named
  com.ibm.websphere.sib.mediation.handler.ejb.GenericEJBMediationH
  andlerLocalHome and a local interface named
  com.ibm.websphere.sib.mediation.handler.ejb.GenericEJBMed
  iationHandlerLocal.
  
  The fix for this APAR is currently targeted for inclusion in
  the WebSphere Application Server Toolkit fixpack 6.0.0.8 and
  Rational Application Developer fixpack 7.0.0.8.  Please refer
  to the following Recommended Updates page for WebSphere
  Application Server Toolkit delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27004980
  and the following Recommended Updates page for Rational
  Application Developer delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27007823
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBAPP SERVER A

• Fixed component ID

  5724J0820

Applicable component levels

• R610 PSY

     UP